Summary

• Verification Strategy pipeline: Design Doc defines how correctness is proven (Correctness Proof Method + Early Verification Point). Work Plan carries the strategy summary. Task files include Operation Verification Methods derived from the strategy. document-reviewer enforces existence (Gate 0) and quality (Gate 1).
• Adaptive Phase Division: Phase structure now adapts to implementation approach — vertical slice produces value-unit phases, horizontal retains Foundation → Core → Integration → QA, hybrid uses vertical as base. Plan template provides Option A/B with explicit delete-unused instruction.
• Agent cross-reference removal: Agent definitions no longer name other agents. Orchestration layers own routing decisions. Input contracts describe format expectations instead of naming producers.
• Japanese terminology unification: 確認レベル → 検証レベル across all agents, skills, and skills-index.

Test plan

• Verify Verification Strategy section in Design Doc template renders correctly
• Verify Plan template Option A/B hierarchy (###/####/#####) is parsed correctly by task-decomposer
• Verify document-reviewer Gate 0 flags missing Verification Strategy
• Verify skills-index.yaml tags match actual skill section names
• Verify Japanese translations are consistent with English counterparts

🤖 Generated with Claude Code